Update the certificate lookup endpoint#747
Merged
JakeWarner merged 2 commits intomainfrom Oct 31, 2025
Merged
Conversation
…rds and make private keys optional.
mattoni
added
enhancement
JakeWarner
approved these changes
Oct 31, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The platform change to the API brings support for looking up user provided certificates on the certificate lookup endpoint. It removes the need to pass the optional wildcard parameter, and simply returns the relevant certificate information that domain would use.
Breaking: You must now pass
private=trueURL parameter in order to receive the private key in the response. This will still require thedns-certs-viewcapability, but fetching without the private key no longer will.